Skip to content

Conversation

@anpingli
Copy link
Contributor

@anpingli anpingli commented Oct 13, 2025

  • Run Logging UI test using real test data
  • defined an individual entrypoint run-cypress-logging.sh
  • update cypress:run:ci and web/cypress.config.ts to make the CI run as-is.
  • Test Logging using both cluster-admin and common users
  • Run Logging test on both Admin Console and Dev Console
  • Run Logging test on both Observer->Logs, and Pod->aggr logs

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 13, 2025
@openshift-ci openshift-ci bot requested review from kyoto and zhuje October 13, 2025 07:28
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 13, 2025
@anpingli anpingli changed the title Logging-ui-plugin test using real user [WIP]Logging-ui-plugin test using real user Oct 13, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 13, 2025
@anpingli anpingli force-pushed the real-user-test branch 8 times, most recently from 86bc31f to 856f0b1 Compare November 24, 2025 10:17
@zhuje
Copy link
Contributor

zhuje commented Nov 24, 2025

/retest

@zhuje
Copy link
Contributor

zhuje commented Nov 24, 2025

@anpingli There are some errors coming from the package-lock.json file, this is from prow logs:

npm error "npm ci" can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with "npm install" before continuing. npm error

@anpingli anpingli force-pushed the real-user-test branch 9 times, most recently from 3294a38 to cf23167 Compare December 3, 2025 13:27
@anpingli anpingli changed the title [WIP]Logging-ui-plugin test using real user ]Logging-ui-plugin test using real data Dec 3, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 3, 2025
@anpingli anpingli changed the title ]Logging-ui-plugin test using real data Logging-ui-plugin test using real data Dec 3, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 6, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 6, 2026
@anpingli
Copy link
Contributor Author

anpingli commented Jan 6, 2026

@etmurasaki @jgbernalp Refactored the program to improve readability and maintainability, please take a look again.

@anpingli anpingli force-pushed the real-user-test branch 4 times, most recently from eb8389d to be6f2a5 Compare January 12, 2026 08:01
@anpingli
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@anpingli: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jgbernalp jgbernalp changed the title Logging-ui-plugin test using real data NO-JIRA: Logging-ui-plugin test using real data Jan 14, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 14, 2026
@openshift-ci-robot
Copy link

@anpingli: This pull request explicitly references no jira issue.

Details

In response to this:

  • Run Logging UI test using real test data
  • defined an individual entrypoint run-cypress-logging.sh
  • update cypress:run:ci and web/cypress.config.ts to make the CI run as-is.
  • Test Logging using both cluster-admin and common users
  • Run Logging test on both Admin Console and Dev Console
  • Run Logging test on both Observer->Logs, and Pod->aggr logs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jgbernalp
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anpingli, jgbernalp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2026
@anpingli
Copy link
Contributor Author

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jan 23, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit a6ab0b5 into openshift:main Jan 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants